Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1502

reference: 729-tree-1
name: 1502
tree-preservation-order: undefined
729-tpo-1
uprn
address-text
point: POINT (-0.988289 50.859728)
geometry: MULTIPOLYGON (((-0.988218 50.859720,-0.988221 50.859734,-0.988231 50.859747,-0.988247 50.859757,-0.988266 50.859763,-0.988288 50.859766,-0.988310 50.859764,-0.988330 50.859758,-0.988346 50.859748,-0.988356 50.859735,-0.988360 50.859721,-0.988357 50.859707,-0.988347 50.859695,-0.988332 50.859685,-0.988312 50.859678,-0.988290 50.859676,-0.988268 50.859678,-0.988248 50.859684,-0.988232 50.859694,-0.988222 50.859706,-0.988218 50.859720)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL